home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.20030409-20031118
/
000360_RM.TAG.brhc@lehigh.edu_Fri Oct 31 14:48:17 2003.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Path: newsmaster.cc.columbia.edu!panix!news.maxwell.syr.edu!newshosting.com!news-xfer1.atl.newshosting.com!diablo.voicenet.com!nntp.upenn.edu!Lehigh.EDU!usenet
From: Bryan Hodgson <RM.TAG.brhc@lehigh.edu>
Newsgroups: comp.protocols.kermit.misc
Subject: Direct connection across a USB-connected DB9.
Date: Fri, 31 Oct 2003 13:21:55 -0500
Lines: 42
Message-ID: <oprxw6mthj3k6cjf@news.lehigh.edu>
NNTP-Posting-Host: dhcp5-181.eecs.lehigh.edu
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset=iso-8859-15
Content-Transfer-Encoding: 8bit
User-Agent: Opera7.21/Win32 M2 build 3218
Xref: newsmaster.cc.columbia.edu comp.protocols.kermit.misc:14615
My latest laptop lacks a DB-9 serial port, useful to me for connecting to
device consoles. So I purchased the laptop vendor's recommendation, a
Belkin FSU103; basically, it's a DB-9 connector at the end of a USB cable
with some status lights to show that it's plugged in / moving data / no
errors. WXP. Device Manager thinks the device really IS a serial port,
and not a modem. And I dug out my copy of Kermit95, and applied the
latest (01/2003?) updates.
HyperTerminal works fine across this device when connected directly to the
serial port and (for example) /dev/ttya on a Sun, although HyperTerminal
itself is still brain-dead, of course. Enter Kermit.
Using a K95 console with:
Communications Parameters:
Port: com4, speed: 9600, mode: local, modem: generic
Parity: none, stop-bits: (default) (8N1)
Duplex: full, flow: rts/cts, handshake: none
Carrier-watch: off, close-on-disconnect: off
Terminal bytesize: 8, escape character: 29 (^])
Priority: regular
Carrier Detect (CD): Off
Dataset Ready (DSR): On
Clear To Send (CTS): On
Ring Indicator (RI): Off
Data Terminal Ready (DTR): (unknown)
Request To Send (RTS): (unknown)
(arrived at via set line com4; set sp 96; set carr off; set flo /dir) ...
When this session is connected, the terminal displays nothing in response
to keystrokes (e.g. enter), though though the send and receive lights on
the serial port device both flash. If I Alt-X back to the command window
and C again, the terminal suddenly flushes the output of the previous
keystrokes.
I presume that I'm clueless about some critical parameter that Kermit
needs but doesn't have. Suggestions would be appreciated.